Methods for Reducing Call Set Up Times Using Automatic Connection Negotiation

ABSTRACT

Methods and products for reducing the time required to set-up a call are provided. In particular, new functionality to H.324 is added by allowing the transmission of media to commence after a reduced number of H.245 messages have been exchanged by two calling devices. If two terminals involved in a call are capable of automatic connect renegotiation, one or more predetermined logical channels in the two terminals for transmitting media is selected, a message is sent from one terminal to the other terminal to open the predetermined logical channel, and media transmission between the two terminals is commenced.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional PatentApplication No. 60/678,492, filed May 6, 2005, which is herebyincorporated by reference herein in its entirety.

FIELD OF THE INVENTION

The present invention relates to methods and products for improving callset-up time in third generation (3G) terminals such as mobiletelephones, servers, and the like. More particularly, the presentinvention relates to adding new functionality to the H.324 protocol forsetting up channels for media delivery in 3G video telephony to allowfor faster call set-up times.

BACKGROUND OF THE INVENTION

ITU H.324 Recommendation, which is hereby incorporated by referenceherein in its entirety, dictates the protocol that is used with 3Gterminals in setting up media channels for media transmission. As partof this protocol, messages specified in ITU H.245 Recommendation, whichis hereby incorporated by reference herein in its entirety, areexchanged between a local terminal and a remote terminal.

One problem with H.324 is that call set-up is a long process mainly dueto a series of H.245 messages that are exchanged by two terminals.Today, to open a call with an audio and a video channel, usually ten ormore H.245 messages need to be exchanged. This requires three to tenround trips of messages. Even more messages may be required to handlechannel conflicts or overcome noisy communication lines.

Turning to FIG. 1, a simplified block diagram of two terminalscommunicating via a conventional network is shown. As illustrated, alocal terminal 11 communicates with a remote terminal 12 via a network13. Local terminal 11 and remote terminal 12 may be for example, devicesfor engaging in 3 G communications, and may be wired or wirelessdevices, such as 3G mobile telephones, servers, etc. Network 13 may beany kind of circuit switched network, or any other network that may beused to pass H.324 data. For example, network 13 may be a networksupporting 3G connections such as an Integrated Services Digital Network(ISDN), a Public Switched Telephone Network (PSTN), a TransmissionControl Protocol (TCP) network, and the like.

FIGS. 2A and 2B illustrate an example of how terminals 11 and 12 may setup a call using a conventional H.324 protocol. As shown, at step 21, anH.245 TerminalCapabilitySet request (TCS) message and an H.245MasterSlaveDetermination request (MSD) message are sent from eachterminal and received by the other. The TCS messages indicate therespective capabilities of terminals 11 and 12, such as supported audioand video codecs, supported features and services, supported adaptationlayers, and so on. The MSD messages determine the master/slaverelationship of terminals 11 and 12.

Subsequently, at step 22, each terminal acknowledges the other's TCS andMSD messages by sending an H.245 TerminalCapabilitySetAck response (TCSAck) message and an H.245 MasterSlaveDeterminationAck response (MSD Ack)message. At this point, both terminals recognize the type of codecs theycan use and which of terminals 11 and 12 is the master or the slave ofthis call.

Next, at step 23, H.245 OpenLogicalChannel request (OLC) messages aresent and received by terminals 11 and 12. Generally, a single videochannel and a single audio channel are opened.

H.245 OpenLogicalChannelAck response (OLC Ack) messages, acknowledgingthe receipt of OLC messages, are then sent and received at step 24.Sometimes, H.245 OpenLogicalChannelReject response (OLC Reject) messagesare sent, which might require additional messages to resolve thesituation to be sent.

At step 25, H.245 MultiplexEntrySend request (MES) messages are sent andreceived by terminals 11 and 12 to enable an H.223 multiplexing (MUX)entry table to be exchanged. The H.223 MUX entry table allows terminals11 and 12 to demultiplex the media sent on the opened channels.

Next, at step 26, H.245 MultiplexEntrySendAck response (MES Ack)messages are then sent and received by terminals 11 and 12 toacknowledge the MES message received from the other terminal.

Finally, after this entire exchange of messages, media is sent andreceived at step 27.

As can be seen, the conventional method requires that at least tenmessages be handled by each terminal before media is sent or received.Such a large number of messages introduces a large delay to the callset-up process. Hence, a method for speeding up the call set-up processmay be desirable and may offer many significant advantages over thecurrently utilized call set-up methods. The above illustrates the“best-case” scenario, where all goes well. In cases of problems,retransmissions or additional messages might be required.

SUMMARY OF THE INVENTION

The present invention provides methods and products to reduce the timerequired to set-up a call without reducing the number of H.245 messagesthat are sent or their normal procedures. In particular, the presentinvention adds new functionality to H.324 by allowing the transmissionof media to commence after a reduced number of H.245 messages have beenexchanged by two calling devices.

In some embodiments, the present invention also provides methods andproducts for setting-up a call that includes (a) selecting a defaultmultiplexing entry table, (b) sending a TerminalCapabilitySetAck (TCSAck) message to a receiving terminal, (c) sending aMasterSlaveDeterminationAck (MSD Ack) message to the receiving terminal,(d) sending an OpenLogicalChannel (OLC) message to the receivingterminal, (e) sending media to the receiving terminal using one or morepredetermined multiplex entries, and (f) sending a MultiplexEntrySendrequest (MES) message to the receiving terminal, wherein steps (a)through (e) are carried out concurrently and without waiting foracknowledgements on any of them.

In some embodiments, the present invention also provides methods andproducts for for setting-up a call that includes (a) selecting a defaultmultiplexing entry table, (b) receiving media from a sending terminalusing one or more predetermined logical channels, (c) optionallybuffering the media received in step (b), (d) presenting the media, (e)receiving a TerminalCapabilitySetAck (TCS Ack) message from the sendingterminal, (f) receiving a MasterSlaveDeterminationAck (MSD Ack) messagefrom the sending terminal, (g) receiving a OpenLogicalChannel (OLC)message from the sending terminal, and (h) receiving aMultiplexEntrySend request (MES) message from the sending terminal,wherein steps (a) through (c) are carried out before or concurrentlywith at least one of steps (e) through (h).

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects and advantages of the present invention willbe apparent upon consideration of the following detailed description,taken in conjunction with the accompanying drawings, in which likereference characters refer to like parts throughout, and in which:

FIG. 1 is a simplified block diagram of two terminals communicating viaa network in conventional systems;

FIGS. 2A and 2B illustrate an example of how two terminals may set-up acall using a conventional H.324 protocol;

FIG. 3 is a diagram showing a method for sending and receiving mediausing Automatic Connection Negotiation (ACN) in accordance with certainembodiments of the present invention;

FIG. 4 is a diagram showing a method for sending media from one terminalto another terminal in accordance with certain embodiments of thepresent invention;

FIG. 5 is a diagram showing a method for receiving, at one terminal,media from another terminal in accordance with certain embodiments ofthe present invention;

FIG. 6 is a diagram showing a method for sending and receiving mediawithout bidirectional video support in accordance with certainembodiments of the present invention;

FIG. 7 is a diagram showing a method for sending and receiving mediawith bidirectional video support in accordance with certain embodimentsof the present invention; and

FIG. 8 is a diagram showing a method for sending and receiving mediausing ACN when one terminal rejects a proposed channel from anotherterminal in accordance with certain embodiments of the presentinvention.

DETAILED DESCRIPTION OF THE INVENTION

Methods and products in accordance with the present invention allowtransmission of media considerably sooner than any currently utilizedconventional implementations, such as that shown in FIGS. 2A and 2B.Methods and products in accordance with the present invention mayadvantageously transmit the conventional H.245 messages and the messageexchange may be handled in the same manner as the currently utilizedconventional protocols (e.g., as shown in FIGS. 2A and 2B), with a fewminor differences.

For example, ITU H.324 Recommendation may be modified to incorporateAnnex J (as shown in Tables 1 and 2) along with the acnCapabilityCapability definition below (as shown in Tables 3 through 5).

Annex J ASN.1 OIDs Defined in this Recommendation

TABLE 1 Clause OID reference {itu-t(0) recommendation(0) h(8) 324generic-capabilities(1) 7.7.1 SessionResetCapability(1)} {itu-t(0)recommendation(0) h(8) 324 generic-capabilities(1) TBD acnCapability(2)}

TABLE 2 Capability name SessionResetCapability Capability identifiertype Standard Capability identifier value {itu-t(0) recommendation(0)h(8) 324 generic-capabilities(1) SessionResetCapability(1)} maxBitRateThis parameter is not used. Collapsing This field shall not be used andshall be ignored by receivers. nonCollapsing This field shall not beused and shall be ignored by receivers. nonCollapsingRaw This fieldshall not be used and shall be ignored by receivers. Transport Thisfield shall not be used and shall be ignored by receivers.

The acnCapability Capability Definition

TABLE 3 acnCapability Capability Identifier Capability name:AcnCapability Capability class: Control capability. Capabilityidentifier type: Standard. Capability identifier {itu-t(0)recommendation(0) h(8) 324 generic- value: capabilities(1)acnCapability(2)} maxBitRate: Shall not be included NonCollapsingRaw:This field shall not be included transport: This field shall not beincluded

TABLE 4 acnCapability Parameter - masterBidirectionalVideo Parametername: masterBidirectionalVideo Parameter description: This is acollapsing GenericParameter. If the terminal indicating this parameter'svalue as 1 will be selected as the master of the call, it shall open abidirectional video channel. In this case, the slave shall not open avideo channel using the ACN procedure. If the master of the callindicates this parameter's value as 0, then the slave should open itsown unidirectional channel. Parameter identifier 1 value: Parameterstatus: Shall be present once for capability exchange Parameter type:unsignedMax, with the value 0 or 1 Supersedes: —

TABLE 5 acnCapability Parameter - mediaBuffering Parameter name:mediaBuffering Parameter description: This is a collapsingGenericParameter. A terminal indicating this parameter's value as 1 isable to buffer the incoming media send before the relevant OLC messageis received from the remote terminal, allowing faster call set-up.Parameter identifier 2 value: Parameter status: Shall be present oncefor capability exchange Parameter type: unsignedMin, with the value 0 or1 Supersedes: —

FIG. 3 generally shows how media transmission may begin at an earlierstage of a call set-up in accordance with the present invention ascompared to the conventional method shown in FIGS. 2A and 2B. Asillustrated, the left side of the diagram may represent a terminal 11,which initiates a call, and the right side of the diagram may representa terminal 12, which receives a call.

At step 31, similar to step 21 of the conventional method, terminals 11and 12 may exchange TCS and MSD messages. Unlike the conventionalmethod, however, the TCS message may contain an indication thatterminals 11 and 12 are capable of sending and receiving OLC message andmedia before any MSD Ack, TCS Ack, MES, and/or MES Ack messages arereceived. In certain embodiments, TCS messages from terminals 11 and 12may contain an indication that terminals 11 and 12 are capable of ACN.For example, TCS messages from terminals 11 and 12 may contain anacnCapability parameter, as defined in Annex J and The acnCapabilityCapability Definition above, which signals support of the ACN procedurein terminals 11 and 12.

If the ACN capability is detected by terminals 11 and 12 from incomingTCS messages, terminals 11 and 12 may select the most preferred channelsand send the corresponding OLC messages as shown in step 32. As shown,media transmission 33 from terminals 11 and 12 may begin concurrentlywith or immediately after each terminal has sent the OLC message. Asshown in FIG. 3, OLC messages of each terminal may be sent along withthe TCS Ack and MSD Ack messages at step 32.

Master/slave status for terminals 11 and 12 may be determined once oneor both of these terminals have received the MSD message from terminals12 and 11, respectively (see step 31). Alternatively, master/slavestatus may be determined once one or both of terminals 11 and 12 havereceived the MSD Ack message from terminals 12 and 11, respectively (seestep 32).

To enable media transmission between terminals 11 and 12 on channelswhose opening has not yet been acknowledged, both terminals may utilizea predetermined table, such as a predetermined table that is decided bya special signaling within the TCS message. For example, TCS message maycontain an acnCapability where both terminals are instructed to utilizethe following default MUX table shown in Table 6:

TABLE 6 Default MUX Table Entry 0 shall be reserved for the controlchannel, for facilitating exchange of H.245 messages. Entry 1 shall beused with a repeatCount of untilClosingFlag for the primary audiochannel. Entry 2 shall be used with a repeatCount of untilClosingFlagfor the primary video channel.The primary audio channel may be configured as a non-segmentable channelwhile the primary video channel may be configured as a segmentablechannel. ACN may hence proceed under the assumption that the OLC and MESmessages are acknowledged.

The remaining messages such as OLC Ack, MES, and MES Ack messages may besent and processed in a conventional manner as shown in steps 34 through36. In particular, the MES message at step 35 may send an updated MUXtable that optimizes the multiplexing of the audio and video media.Therefore, if the predetermined MUX table used to initially transmitdata is not optimal, subsequent transmission of the MES message mayeasily mitigate such problems.

In view of the description provided above, methods of the presentinvention may allow media transmission after only half a round tripduring call set-up while maintaining full H.245 functionality ascompared to at least ten messages being handled by each terminal beforemedia is sent or received as shown in FIG. 2.

FIG. 4 illustrates a method for sending media from a terminal 11 to aterminal 12 in accordance with certain embodiments of the presentinvention. Either of terminals 11 or 12 may be a receiving terminal,which receives a call, and/or a sending terminal, which sends a call.Moreover, either of terminals 11 and 12 may be a local terminal or aremote terminal. However, for illustration purposes only, FIG. 4 will bedescribed with the assumption that terminal 11 acts as a local, sendingterminal (capable of ACN) and terminal 12 acts as a remote, receivingterminal.

As shown, at step 40, TCS (e.g., with an acnCapability parameter) andMSD messages may be transmitted from terminal 11 to terminal 12 and TCS(e.g., with an acnCapability parameter) and MSD messages may betransmitted from terminal 12 to terminal 11.

Next, terminal 11 may determine if ACN is going to be used at step 41.This determination may be made by determining whether terminal 12 iscapable of ACN as specified in the TCS message transmitted by terminal12, or may be made in any other suitable manner.

If it is determined that ACN is not going to be used, then the methodmay proceed in a conventional manner as shown in FIGS. 2A and 2B. Forexample, at step 42, terminal 11 may receive TCS Ack and MSD Ackmessages from terminal 12. Then, at step 43, terminal 11 may send TCSAck, MSD Ack, and OLC messages to terminal 12. Terminal 11 may thenreceive OLC Ack message from terminal 12 at step 44. Next, terminal 11may send an MES message to terminal 12 at step 45 and terminal 11 mayreceive an MES Ack message from terminal 12 at step 46. Finally, mediamay be transmitted between terminals 11 and 12 at step 47, and routinetransmission of media may take place after this point as is known in theart.

Returning to step 41, if it is determined that ACN is going to be used,steps 48 through 54 may be carried out. As shown, steps 48 through 50may be performed before or concurrently with steps 51 through 54.

At step 48, a default MUX entry table may be selected. For example, thedefault MUX entry table may be pre-programmed into terminals 11 and 12.Then, at step 49, terminal 11 may send OLC messages to terminal 12.Although steps 48 and 49 are shown being performed in the given order,the order of the steps may be reversed in some circumstances. Next, atstep 50, terminal 11 may begin sending media to terminal 12.

At step 51, terminal 11 may send TCS Ack and MSD Ack messages toterminal 12. Step 51 is usually done in parallel with step 49. Next, atstep 52, terminal 11 may receive an OLC Ack message from terminal 12.Then, at step 53, an MES message may be sent from terminal 11 toterminal 12, and an MES Ack message may be received by terminal 11 fromterminal 12. If necessary, at step 54, the channel selections may beadjusted as indicated in the MES message. Finally, media may be sent toterminal 12 at step 50, as known in the art.

As can be seen, when ACN is used, media may be sent much more quicklythan that possible using conventional methods leading to a substantialdecrease in waiting time for call set-up. By sending media before orconcurrently with performing steps 51 through 54, much of the delay ofsetting up a call can be eliminated.

FIG. 5 illustrates a method for terminal 11 to receive media transmittedfrom terminal 12. As before, either of terminals 11 or 12 may be areceiving terminal, which receives a call, and/or a sending terminal,which sends a call. Moreover, either of terminals 11 and 12 may be alocal terminal or a remote terminal. However, for convenience, FIG. 5will be described with the assumption that terminal 11 acts as a local,receiving terminal (capable of ACN) and terminal 12 acts as a remote,sending terminal.

As shown, at step 60, terminal 12 may receive TCS (e.g., with anacnCapability parameter) and MSD messages from terminal 12. In response,terminal 11 may send TCS (e.g., with an acnCapability parameter) and MSDmessages to terminal 12.

Next, at step 61, terminal 11 may determine whether ACN will be used. Asdescribed above, TCS message from terminal 12 may contain anacnCapability parameter indicating that terminal 12 is also capable ofACN. Alternatively, such a determination may be made in any othersuitable manner.

If it is determined that ACN is not going to be used, then the methodmay proceed to step 62, where terminal 11 sends TCS Ack and MSD Ackmessages to terminal 12. TCS Ack, MSD Ack, and OLC messages fromterminal 12 may then be received by terminal 11 at step 63. Terminal 11may send an OLC Ack message to terminal 12 at step 64. Next, terminal 11may receive an MES message from terminal 12 at step 65 and MES Ack maybe sent to terminal 12 from terminal 11 at step 66. Finally, media maybe received at step 67 and presented at step 68. Routine receipt andpresentation of media may take place after this point as is known in theart.

Returning to step 61, if it is determined that ACN is going to be used,then the method of the present invention may proceed to perform steps 69through 76. As shown, steps 69 through 71 may be performed before orconcurrently with steps 72 through 76.

At step 69, the method may select a default MUX entry table. Forexample, the default MUX entry table may be pre-programmed intoterminals 11 and 12 or signaled within the TCS message. Next, at step70, media from terminal 12 may be received and buffered by terminal 11.The media may then be presented to a user at step 71.

At step 72, TCS Ack and MSD Ack messages from terminal 12 may bereceived at terminal 11 and TCS Ack and MSD Ack messages may be sentfrom terminal 11 to terminal 12. At step 73, terminal 11 may receive OLCmessages from terminal 12. After receiving an OLC message from terminal12, terminal 11 may send an OLC Ack message to terminal 12, and thebuffered media can be presented as shown in step 71. At step 74,terminal 11 may receive an MES message from terminal 12, and an MES Ackmessage may be sent from terminal 11 to terminal 12. If necessary, atstep 75, the channel selections may be adjusted as indicated in the MESmessage. Finally, terminal 11 may continue to receive media at step 76and may continue to present media to a user at step 71 as is known inthe art.

It should noted that various modifications to the invention may beimplemented without departing from the scope of the invention. Forexample, to open logical channels (see, e.g., steps 48, 49, 69, and 70),each terminal may select a set of preferred media types using local andremote capability sets defined above and by using the results of themaster/slave determination process. For example, both the master andslave terminals, as determined by the master/slave determinationmentioned above, may open unidirectional audio channels. Moreover, theslave terminal generally may not need to open any bidirectional channelusing ACN.

The master terminal may also open only a unidirectional video channel ifit has not indicated that it will not open a bidirectional video channelusing the masterBidirectionalVideo parameter defined in Table 4. FIG. 6shows a diagram of a method for sending and receiving media without abidirectional video preference in the master terminal. As illustrated,the method shown in FIG. 6 is generally similar to the method shown inFIG. 3, except FIG. 6 explicitly shows the OLC messages to contain OLC(Audio) and OLC (Video) (see step 80) and OLC Ack messages to containOLC Ack (Audio) and OLC Ack (Video) messages (see step 81).

Alternatively, the master terminal may open a bidirectional videochannel using ACN if it has specified the masterBidirectionalVideoparameter in the TCS message and if both the master and the slaveterminals can use video with an adaptation layer that supportsretransmissions (i.e., AL3, AL1M, or AL3M). FIG. 7 shows a diagram of amethod for sending and receiving media with a bidirectional videopreference in the master terminal. As shown, the steps carried out maybe similar to that shown in FIG. 6, except that this method may requiresending an OLC Confirm (Video) message (see step 82) along with the MESmessage from the master terminal to the slave terminal.

In certain instances, a slave terminal may receive an OLC message from amaster terminal and may reject the proposed channel, ignoring any mediareceived for this channel. The slave terminal may also decide not tobuffer any incoming media for this media type until a new OLC message isreceived for it from the master terminal. For example, FIG. 8 shows oneembodiment of the invention where the video channel proposed by themaster terminal is rejected by the slave terminal. The slave terminalmay then send out a OpenLogicalChannelReject (OLC Reject) message forthe video channel back to the master terminal (step 83).

The master terminal may then propose to open a different video channelusing the regular OLC procedure or the ACN procedure (step 84). Then,the master terminal may receive an OLC Ack message from the slaveterminal (step 85) and send media to the slave terminal again (step 86).Alternatively, the master terminal may decide to wait 2 seconds(measured from the time it last sent media on the rejected channel) (orany other appropriate amount of time) before resending the media to theslave terminal although an OLC Ack message has not been received.

In certain embodiments of the present invention, the methods describedabove may be embodied as a software product residing on a computerreadable medium, such as a floppy disk, CD-ROM, DVD-ROM, hard disk,memory chip such as a programmable read-only-memory, erasableprogrammable read-only memory, electrically erasable programmableread-only memory, flash memory, random access memory, etc., or any otherequivalents thereof. In particular, the products in accordance with thepresent invention may reside as a software in a device capable of 3Gtelephony, such as a mobile telephone, servers, terminals 11 and 12, orany other equivalents thereof.

Upon review of the description and embodiments of the present invention,those skilled in the art will understand that modifications andequivalent substitutions may be performed in carrying out the inventionwithout departing from the essence of the invention. Thus, the inventionis not meant to be limiting by the embodiments described explicitlyabove, and is limited only by the claims which follow.

1-39. (canceled)
 40. A method for reducing call setup times on aterminal, the method comprising: sending a TerminalCapabilitySetmessage, a MasterSlaveDetermination message, and at least oneOpenLogicalChannel message to a receiving terminal; and sending media tothe receiving terminal on one or more channels opened with the at leastone OpenLogicalChannel message before receiving, from the receivingterminal, one or more of: an acknowledgement message for theTerminalCapabilitySet message, an acknowledgement message for theMasterSlaveDetermination message, and at least one acknowledgementmessage for the at least one OpenLogicalChannel message.
 41. The methodof claim 40, wherein the at least one OpenLogicalChannel message and themedia are sent simultaneously.
 42. The method of claim 40, furthercomprising opening the one or more channels in accordance with one ormore signals comprised in the TerminalCapabilitySet message.
 43. Themethod of claim 40, wherein at least one of the opened channels is oneof: a unidirectional audio channel, a bidirectional video channel, and aunidirectional video channel.
 44. The method of claim 40, wherein theTerminalCapabilitySet message includes an indication that a sendingterminal is capable of sending the media to the receiving terminalbefore receiving, from the receiving terminal, one or more of: theacknowledgement message for the TerminalCapabilitySet message, theacknowledgement message for the MasterSlaveDetermination message, andthe at least one acknowledgement message for the at least oneOpenLogicalChannel message.
 45. A method for reducing call setup timeson a terminal, the method comprising: receiving a TerminalCapabilitySetmessage, a MasterSlaveDetermination message, and at least oneOpenLogicalChannel message from a sending terminal; and receiving mediafrom the sending terminal on one or more channels opened with the atleast one OpenLogicalChannel message before sending one or more of: anacknowledgement message for the TerminalCapabilitySet message, anacknowledgement message for the MasterSlaveDetermination message, and atleast one acknowledgement message for the at least oneOpenLogicalChannel message.
 46. The method of claim 45, wherein the atleast one OpenLogicalChannel message and the media are receivedsimultaneously.
 47. The method of claim 45, wherein at least one of theopened channels is one of: a unidirectional audio channel, abidirectional video channel, and a unidirectional video channel.
 48. Themethod of claim 45, further comprising buffering the received media. 49.The method of claim 48, wherein the received media is buffered until theOpenLogicalChannel message associated with the received media isreceived.
 50. A method for reducing call setup times on a terminal, themethod comprising: sending a TerminalCapabilitySet message from asending terminal to a receiving terminal, wherein theTerminalCapabilitySet message includes an indication that the sendingterminal is capable of sending at least one OpenLogicalChannel messageand media before receiving, from the receiving terminal, one or more of:an acknowledgement message for the TerminalCapabilitySet message, anacknowledgement message for the MasterSlaveDetermination message, and atleast one acknowledgement message for the at least oneOpenLogicalChannel message.
 51. The method of claim 50, wherein theindication further indicates that the sending terminal is capable ofsending the at least one OpenLogicalChannel message and media beforeoptionally sending a MultiplexEntrySend message.
 52. The method of claim50, further comprising: sending the at least one OpenLogicalChannelmessage to the receiving terminal; and sending the media to thereceiving terminal on one or more channels opened with the at least oneOpenLogicalChannel message.
 53. The method of claim 52, wherein the atleast one OpenLogicalChannel message and the media are sentsimultaneously.
 54. The method of claim 50, wherein the indicationincluded in the TerminalCapabilitySet further comprises a defaultmultiplexing entry table.
 55. The method of claim 54, further comprisingsending a MultiplexEntrySend message that updates the defaultmultiplexing entry table.
 56. The method of claim 50, further comprisingselecting a default multiplexing entry table according to one or moresignals comprised in the TerminalCapabilitySet message.
 57. The methodof claim 56, further comprising sending a MultiplexEntrySend messagethat updates the default multiplexing entry table.
 58. A method forreducing call setup times on a terminal, the method comprising: sendinga TerminalCapabilitySet message from a receiving terminal to a sendingterminal, wherein the TerminalCapabilitySet includes an indication thatthe receiving terminal is capable of receiving at least oneOpenLogicalChannel message and media before sending, to the sendingterminal, one or more of: an acknowledgement message for theTerminalCapabilitySet message, an acknowledgement message for aMasterSlaveDetermination message, and at least one acknowledgementmessage for the at least one OpenLogicalChannel message.
 59. The methodof claim 58, further comprising: receiving the at least oneOpenLogicalChannel message from the sending terminal; and receiving themedia from the sending terminal on one or more channels opened with theat least one OpenLogicalChannel message.
 60. The method of claim 59,wherein the media begins to be received before the OpenLogicalChannelmessage associated with the media is received.
 61. The method of claim58, wherein the indication included in the TerminalCapabilitySet messagefurther comprises a default multiplexing entry table.
 62. The method ofclaim 61, further comprising receiving a MultiplexEntrySend message thatupdates the default multiplexing entry table.
 63. The method of claim58, further comprising selecting a default multiplexing entry tableaccording to one or more signals comprised in the TerminalCapabilitySetmessage.
 64. The method of claim 63, further comprising receiving aMultiplexEntrySend message that updates the default multiplexing entrytable.
 65. A method for reducing call setup times on a terminal, themethod comprising: selecting a default multiplexing entry tableaccording to one or more signals comprised in a TerminalCapabilitySetmessage; sending at least one OpenLogicalChannel message to a receivingterminal; sending media to the receiving terminal using one or morechannels opened with the at least one OpenLogicalChannel message beforereceiving one or more of: an acknowledgement message for theTerminalCapabilitySet messages an aclnowledgement message for aMasterSlaveDetermination message, and at least one acknowledgementmessage for the at least one OpenLogicalChannel message; and sending aMultiplexEntrySend message that updates the default multiplexing entrytable.
 66. The method of claim 65, wherein the at least oneOpenLogicalChannel message and the media are sent simultaneously. 67.The method of claim 65, further comprising: sending theTerminalCapabilitySet message to the receiving terminal; receiving asecond TerminalCapabilitySet message from the receiving terminal; andselecting the default multiplexing entry table in response to sendingthe TerminalCapabilitySet message and receiving the secondTerminalCapabilitySet message.
 68. The method of claim 65, furthercomprising opening the one or more channels in accordance with one ormore signals comprised in the TerminalCapabilitySet message.
 69. Themethod of claim 65, wherein at least one of the opened channels is oneof: a unidirectional audio channel, a bidirectional video channel, and aunidirectional video channel.
 70. The method of claim 65, wherein theTerminalCapabilitySet message includes an indication that the sendingterminal is capable of sending the media to the receiving terminalbefore receiving, from the receiving terminal, one or more of theacknowledgement messages.
 71. A method for reducing call setup times ona terminal, the method comprising: receiving at least oneOpenLogicalChannel message from a sending terminal; receiving media fromthe sending terminal using the plurality of channels before sending oneor more of: an acknowledgement message for a TerminalCapabilitySetmessage, an acknowledgement message for a MasterSlaveDeterminationmessage, at least one acknowledgement message for the at least oneOpenLogicalChannel message; and in response to receiving anOpenLogicalChannel message and the media associated with theOpenLogicalChannel message, sending an OpenLogicalChannelReject messagefor rejecting that channel and ignoring the media sent on that channelfrom the sending terminal.
 72. The method of claim 71, wherein the atleast one OpenLogicalChannel message and the media are receivedsimultaneously.
 73. The method of claim 71, wherein the at least one ofthe plurality of channels is one of: a unidirectional audio channel, abidirectional video channel, and a unidirectional video channel.
 74. Themethod of claim 71, further comprising receiving a message that proposesto open one or more logical channels that are different from therejected channel.
 75. The method of claim 74, further comprising sendingan acknowledgement message for the message that opens one or morelogical channels that are different from the rejected channel.
 76. Amethod for reducing call setup times on a terminal, the methodcomprising: sending at least one OpenLogicalChannel message to areceiving terminal; sending media from the receiving terminal on theplurality of channels before receiving one or more of: anacknowledgement message for a TerminalCapabilitySet message, anacknowledgement message for a MasterSlaveDetermination message, at leastone acknowledgement message for the at least one OpenLogicalChannelmessage; and in response to sending an OpenLogicalChannel message andthe media associated with the OpenLogicalChannel message, receiving anOpenLogicalChannelReject message for rejecting that channel.
 77. Themethod of claim 76, wherein the at least one OpenLogicalChannel messageand the media are sent simultaneously.
 78. The method of claim 76,wherein the at least one of the plurality of channels is one of: aunidirectional audio channel, a bidirectional video channel, and aunidirectional video channel.
 79. The method of claim 76, furthercomprising sending a message that proposes to open one or more logicalchannels that are different from the rejected channel.
 80. The method ofclaim 79, further comprising receiving an acknowledgement message forthe message that opens one or more logical channels that are differentfrom the rejected channel.
 81. A method for reducing call setup times ona terminal, the method comprising: sending, from a sending terminal, atleast one OpenLogicalChannel message to a receiving terminal beforereceiving a TerminalCapabilitySetAck message and aMasterSlaveDeterminationAck message from the receiving terminal; andsending media to the receiving terminal on one or more logical channelsopened with the at least one OpenLogicalChannel message before receivingat least one OpenLogicalChannelAck message from the receiving terminal.82. The method of claim 81, wherein the at least one OpenLogicalChannelmessage and the media are sent simultaneously.
 83. The method of claim81, further comprising opening the one or more channels in accordancewith one or more signals comprised in a TerminalCapabilitySet message.84. The method of claim 81, wherein at least one of the opened channelsis one of: a unidirectional audio channel, a bidirectional videochannel, and a unidirectional video channel.
 85. The method of claim 81,further comprising selecting a default multiplexing entry tableaccording to one or more signals comprised in a TerminalCapabilitySetmessage.
 86. The method of claim 81, further comprising selecting adefault multiplexing entry table according to one or more signalscomprised in TerminalCapabilitySet messages exchanged between thesending terminal and the receiving terminal.
 87. The method of claim 81,further comprising sending a MultiplexEntrySend request message to thereceiving terminal.
 88. The method of claim 81, further comprisingsending another message to the receiving terminal to open one or morelogical channels different from the one or more logical channels openedwith the at least one OpenLogicalChannel message.
 89. A method forreducing call setup times on a terminal, the method comprising:receiving, at a receiving terminal, at least one OpenLogicalChannelmessage from a sending terminal before sending aTerminalCapabilitySetAck message and a MasterSlaveDeterminationAckmessage to the sending terminal; and receiving media from the sendingterminal on one or more logical channels opened with the at least oneOpenLogicalChannel message before sending at least oneOpenLogicalChannelAck message to the sending terminal.
 90. The method ofclaim 89, wherein the at least one OpenLogicalChannel message and themedia are received simultaneously.
 91. The method of claim 89, furthercomprising opening the one or more channels in accordance with one ormore signals comprised in a TerminalCapabilitySet message.
 92. Themethod of claim 89, wherein at least one of the opened channels is oneof: a unidirectional audio channel, a bidirectional video channel, and aunidirectional video channel.
 93. The method of claim 89, furthercomprising selecting a default multiplexing entry table according to oneor more signals comprised in the a TerminalCapabilitySet message. 94.The method of claim 89, further comprising selecting a defaultmultiplexing entry table according to one or more signals comprised inTerminalCapabilitySet messages exchanged between the sending terminaland the receiving terminal.
 95. A method for reducing call setup timeson a terminal, the method comprising: sending a firstTerminalCapabilitySet message from a sending terminal to a receivingterminal, wherein the first TerminalCapabilitySet includes a firstindication that the sending terminal is capable of sending at least oneOpenLogicalChannel message and media before receiving, from thereceiving terminal, one or more of: an acknowledgement message for thefirst TerminalCapabilitySet message, an acknowledgement message for aMasterSlaveDetermination message, and at least one acknowledgementmessage for the at least one OpenLogicalChannel message; receiving asecond TerminalCapabilitySet message from the receiving terminal,wherein the second TerminalCapabilitySet includes a second indicationthat the receiving terminal is capable of receiving the at least oneOpenLogicalChannel message and the media before sending one or more of:the acknowledgement message for the first TerminalCapabilitySet message,the acknowledgement message for the MasterSlaveDetermination message,and the at least one acknowledgement message for the at least oneOpenLogicalChannel message; and in response to receiving the secondTerminalCapabilitySet message, simultaneously sending the at least oneOpenLogicalChannel message and the media to the receiving terminal onone or more logical channels opened with the at least oneOpenLogicalChannel message.
 96. The method of claim 95, furthercomprising selecting a default multiplexing entry table according to oneor more signals comprised in the first and second TerminalCapabilitySetmessages exchanged between the sending terminal and the receivingterminal.
 97. A method for reducing call setup times on a terminal, themethod comprising: receiving a first TerminalCapabilitySet message froma sending terminal to a receiving terminal, wherein the firstTerminalCapabilitySet includes a first indication that the sendingterminal is capable of sending at least one OpenLogicalChannel messageand media before receiving, from the receiving terminal, one or more of:an acknowledgement message for the first TerminalCapabilitySet message,an acknowledgement message for a MasterSlaveDetermination message, andat least one acknowledgement message for the at least oneOpenLogicalChannel message; sending a second TerminalCapabilitySetmessage to the sending terminal, wherein the secondTerminalCapabilitySet includes a second indication that the receivingterminal is capable of receiving the at least one OpenLogicalChannelmessage and the media before sending one or more of: the acknowledgementmessage for the first TerminalCapabilitySet message, the acknowledgementmessage for the MasterSlaveDetermination message, and the at least oneacknowledgement message for the at least one OpenLogicalChannel message;and in response to sending the second TerminalCapabilitySet message,simultaneously receiving the at least one OpenLogicalChannel message andthe media on one or more logical channels opened with the at least oneOpenLogicalChannel message.
 98. The method of claim 97, furthercomprising selecting a default multiplexing entry table according to oneor more signals comprised in the first and second TerminalCapabilitySetmessages exchanged between the sending terminal and the receivingterminal.